Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add FAQ for inspec exec errors when gcp transport is not specified. … #15

Merged
merged 1 commit into from
Jun 6, 2018

Conversation

skpaterson
Copy link

…See https://discourse.chef.io/t/inspec-gcp-issue/13124 for background.

Signed-off-by: Stuart Paterson [email protected]

@skpaterson skpaterson requested a review from chris-rock May 31, 2018 08:39
Copy link
Contributor

@miah miah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @skpaterson

Copy link
Contributor

@chris-rock chris-rock left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @skpaterson Is there a way to make the response more human-readable in InSpec/Train?

@chris-rock chris-rock merged commit e6a2cc0 into master Jun 6, 2018
@skpaterson
Copy link
Author

Would it be a good idea to add an inspec.yml profile setting for platform name / transport? That way we could enforce e.g. AWS, Azure, GCP, ...

@skpaterson skpaterson deleted the add-gcp-transport-readme branch June 14, 2018 13:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants